1. You want to update or upgrade an existing SAP NetWeaver AS ABAP based system using the Software Update Manager tool with version 2.0 SP15, and in the course of this you want to migrate your existing

• SAP BW system
• SAP for Banking system
• SAP Business Suite system
• SAP NetWeaver ABAP stack based system

to one of the following databases:

• SAP HANA database
• SAP Adaptive Server Enterprise (SAP ASE)
• Microsoft SQL Server (available on request, see details below)
• IBM Db2 for Linux, UNIX, and Windows (DB6)  (available on request, see details below)
• SAP MaxDB (available on request, see details below)

Note that source and target database and database type as well must be different. That is, a homogenous migration is not supported.

2. You want to carry out only a migration of your SAP system to the SAP HANA or SAP MaxDB database, but you do not intend to update the SAP system, and hence you do not need to provide a stack.xml file. For more information about this feature, see the topic "Using DMO without System Update" in the "2 Planning" section of the DMO Guide for target database SAP HANA.

For a graphical representation of the supported update and upgrade paths, see also the PDF-documents attached to this SAP Note.

This SAP Note covers the following:

• constraints and restrictions
• problems in the update/upgrade and migration process
• errors in the guide "Database Migration Option (DMO) of SUM"
• additional information to this guide
• problems in the planning and preparations.

This SAP Note refers to the Database Migration Option of SUM 2.0 SP15. All comments and corrections contained in the central SUM 2.0 SP15 Note 3146834 are also relevant for your update and DMO process.

SUM 2.0, Software Update Manager, support package installation, EHP, enhancement package, HANA, database, migration, DMO, database migration option

The Software Update Manager (SUM) is equipped with the feature database migration option (DMO). This option helps you avoiding landscape changes (SID, host name). The SUM tool combines the relevant steps for the in-place migration: Upgrade, and Migration. Further benefits are the reduced Business Downtime and the remaining consistency of the source database so that a fast fallback is possible.

Documentation

This SAP Note accompanies the DMO guide "Database Migration Option: Target Database <database>", which is a supplement to the SUM guide "Updating SAP <technology> Systems on <operating system>: <database>.
Both guides are available on the SAP Help Portal: http://support.sap.com/sltoolset. Choose tab "System Maintenance", then "Database Migration Option (DMO) using SUM".

If you use a lower SUM version, make sure that you have the DMO guide and the SUM guide at hand that are related to this SUM version.

It is also essential that you pay attention to the guides mentioned in the section "Introduction" -> "Integration/Further Documentation" of the DMO guide, as well as to the SAP Notes listed in this guide in section "Introduction" -> Before You Start -> SAP Notes".

Note: Before you start using the SUM tool with database migration option, make sure that you have the latest version of the corresponding documents and SAP Notes!

 

General prerequisites

• ABAP stack only
• Source SAP system must be a Unicode system
• Target release: System based on SAP NetWeaver 7.5 (or higher). For target releases of SAP_BASIS 740, you need to use SUM 1.1.
• See also the "Release restrictions and Limitations" and "Restrictions regarding databases and operating systems" in section I/ below"!
  

Prerequisites for SAP BW systems

• Start release: SAP BW 7.00 (or higher)
• at least SP17 required for software component SAP_BASIS 700
• at least SP02 required for software component SAP_BASIS 701
• at least SP19 required for software component SAP_BW 700
• at least SP02 required for software component SAP_BW 701

For a graphical representation of the supported update and upgrade paths, see also the PDF-documents attached to this SAP Note.

Prerequisites for SAP Business Suite systems

-----< Update D029945 25/JUN/2018 >--------

• Start release:
• SAP ERP 6.0 or higher (for example EHP1, EHP2, EHP3)
• Systems based on SAP NetWeaver 7.0 (for example SAP ERP 6.0) need at least SP17 for software component SAP_BASIS and SP19 for software component SAP_BW
• Systems as part of SAP Business Suite 7 or higher (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0)
• SAP SCM 7.0 (or higher)
• Additional limitation for SCM systems with integrated liveCache: For the migration of an SCM liveCache to an integrated SAP HANA liveCache on an SAP HANA database within the SUM DMO procedure, the following minimum support package (SP) levels of the SAP SCM start releases are required: SAP SCM 7.0 as of SP11, SAP SCM 7.0 EHP1 as of SP09, SAP SCM EHP2 as of SP10, or a higher SAP SCM version. For further information, see SAP Note 1825703.
  The SUM DMO procedure can execute all manual steps of this SAP Note automatically, except the installation of the SAP liveCache applications and the finale liveCache test with transaction LCA03. Hence make sure that SAP liveCache applications (SAP LCA or LCAPPS-Plugin) are installed on the SAP HANA database before you migrate an SCM liveCache.
• Note: This additional limitation of the SAP SCM start release SP level is not necessary for a migration of an SCM system without integrated SAP HANA liveCache.
• If you want to use planning object structures in an SAP SCM system installed on an SAP HANA database, you have to migrate planning object structures after the SUM DMO procedure but BEFORE productive usage. For further information, see SAP Note 1818080.
• SAP BW 7.00 (or higher)
• Systems based on SAP NetWeaver 7.0 at least SP17 for software component SAP_BASIS and SP19 for software component SAP_BW

For a graphical representation of the supported update and upgrade paths, see also the PDF-documents attached to this SAP Note.

 

Organizational remarks

• We recommend to involve a certified consultant "OS/DB migration for SAP NetWeaver", but this is not required.
• It is NOT required or mandatory to include the "OS/DB Migration Check Service" for a DMO run, neither for the productive system nor for other systems, although it is a useful and recommended service.

 

*** This SAP Note is updated on a regular basis. Make sure that you have the latest version of this SAP Note before you start the upgrade/update with DMO. ***

 

Part A: General Problems / Information

Contents

I/....... Important General Information
II/ ..... Corrections/Addenda to the Guide or Online Help
III/ .... Preparing the Update/Upgrade with DMO
IV/..... Problems during the Update/Upgrade with DMO
V/ ..... Problems after the Update/Upgrade with DMO

 

I/....... Important General Information:

Restrictions and Limitations:

Below, you will be informed about the following restrictions and limitations:

• a) General Release Restrictions and Limitations
• b) Restrictions Regarding Databases, Operating Systems, and Platforms
• b1) Operating Systems and Platforms
• b2) Source Databases
• b3) Target Databases
• I) SAP HANA
• II) SAP ASE
• III) MS SQL
• IV) IBM Db2 for Linux, UNIX, and Windows (DB6)
• V) SAP MaxDB
• c) "DMO with System Move": Requirements and Restrictions
• d) Downtime-Optimized DMO
• e) Downtime-Optimized Conversion to SAP S/4HANA

 

--------------< Last Update D029945 11/MAY/2020 >---------------------
a) General Release Restrictions and Limitations

• DMO keeps the application server stable. This means that you start the SUM tool on a dedicated host on which there is an instance of the application server, and both the instance and the host are not changed during the DMO procedure. The only exception is the scenario "DMO with system move", in which the application server can be changed during the DMO procedure.
  Note that although the option "ASCS instance move" allows you to change the ASCS instance, the application server on which you start the SUM tool is not changed (host and instance).
  However, it is possible to install application servers before or after the DMO procedure. You can switch to them after the SUM with DMO run is completed.
• Using DMO for a migration across data center is not supported (PAS host and DB host in different data center). There are no technical restrictions, but it comes with a high performance and latency impact. You may use it at your own risk. No support is provided in case of performance issues or broken procedures due to network/latency issues. Consider "DMO with System Move" instead.
• Note that SAP is currently investigating possibilities and boundaries of using DMO (without "system move" option) for a system conversion to SAP S/4HANA combined with a data center move. We are looking for customer projects as Proof-of-Concept to verify our assumptions. If this may be interesting for your project, contact us by creating an incident on component BC-UPG-TLS-TLA with title "Registration for conversion with data center move". Specify the source database size, rough timeline, and locations of source and target environments.
• If you move to hyperscaler Microsoft Azure, you may check the whitepaper "Converting from SAP ERP on Premise to SAP S/4HANA on Microsoft Azure" published at https://www.sap.com/documents/2021/12/a8fcb608-097e-0010-bca6-c68f7e60039b.html.
• Product Version SAP NW AS for ABAP 7.51 Innovation Package is not offered as possible target release for the DMO scenario.
  (Note that this limitation does not apply for the system conversion to SAP S/4HANA 1610, because SAP S/4HANA 1610 is based on software component SAP_BASIS 751  and not on this specific SAP NetWeaver product version SAP NW AS for ABAP 7.51 IP.)
• Product Version SAP NW AS for ABAP 7.52 is not offered as possible target release for the DMO scenario.
  (Note that this limitation does not apply for the system conversion to SAP S/4HANA 1709, because SAP S/4HANA 1709 is based on software component SAP_BASIS 752  and not on this specific SAP NetWeaver product version SAP NW AS for ABAP 7.52.)

----------------< Last update D031330 02/JUN/2021 >---------------------------
b) Restrictions Regarding Databases, Operating Systems, and Platforms

b1) Operating Systems and Platforms

• Operating system of application server: The operating system of the application server(s) has to be supported for the target SAP release as well as the source SAP release according to PAM.
• For System Move only: The operating system of the application server on the source host has to be supported for the source SAP release according to PAM. The operating system of the application server on the target host has to be supported for the target SAP release according to PAM.
• If target SAP_BASIS is 755 or higher, the Linux distributions mentioned in the following are allowed in addition. However, they are allowed only temporarily for the period of the migration, that is, only during the SUM run. Afterwards, you have to update them to the supported versions that are listed in PAM.
• SUSE Linux Enterprise Server 12 (SLES12)
• Red Hat Enterprise Linux 7 (RHEL7)
• If target SAP_BASIS is 753 or higher and your application server is based on Windows, consider SAP Note 2734697

 

b2) Source Databases

CAUTION: No usage of source database after SUM with DMO run. This is only possible if you perform a "DMO with System Move".

After a normal SUM with DMO run (that is, you do NOT perform a "DMO with System Move" as described in the guide), the source database cannot be used as a database for an SAP system, since artifacts remain. Note that DMO does not allow a parallel usage of source and target database.

A use of the source database after the SUM with DMO run would only be possible by executing a DMO reset. This resets the SAP system to its source release and source database, but it deletes also the content from the target database (see also section 5.3 in the DMO guide). If you want to use the source and target systems in parallel, you will have to execute a system copy before starting the DMO run, and then execute DMO on one system only.

 

b3) Target Databases

Please note:
In the following you find the information about source and target databases that are required for a successful database migration during a system update (SUM with DMO). However, the database versions may differ in other SAP Notes related to products running on the databases, such as SAP Note 2158828, which deals with minimal DB system platform requirements for SAP NetWeaver 7.5.
Example: You need at least SAP HANA 1.0 revision 90 or higher for a successful migration of the source database to SAP HANA database, but according to SAP Note 2158828 you need at least SAP HANA SPS09, Revision 97, if you want to run SAP NetWeaver 7.5 ABAP on SAP HANA.

Overview: Which source database supports which target database?

 

I) Target Database SAP HANA

• Required is SAP HANA 1.0 revision 90 or higher.

Requirements depending on the source database:

 All other database types according to PAM.

 

II) Target Database SAP ASE

• Source SAP systems based on SAP_BASIS 730: Supported minimum support package of SAP_BASIS 730 is SP04

 Requirements depending on the source database:

 All other database types according to PAM.

 

III) Target Database MS SQL

• Currently only available on request. If you are interested in MS SQL as target database,
  contact SAP by reporting an incident on component BC-UPG-TLS-TLA that contains the following data:
  • details about the source and target levels regarding operating system, database, and ABAP
  • information about Unicode
  • a request to forward the incident directly to development support
• Source SAP system must base on the following minimum start releases:
• 700 SP 16
• 701 SP 06
• 702 SP 03
• 710 SP 09
• 711 SP 05
• 730 SP 02
• 731 SP 00
• 740 SP 00
• The operating system of all application server instances has to be Windows.

Requirements depending on the source database:

 All other database types according to PAM.

 

IV) Target Database IBM Db2 for Linux, UNIX, and Windows (DB6)

• Currently only available on request. If you are interested in DB6 as target database,
  contact SAP by reporting an incident on component BC-UPG-TLS-TLA that contains the following data:
  • details about the source and target levels regarding operating system, database, and ABAP
  • information about Unicode
  • a request to forward the incident directly to development support
  .
• Use the latest 753 kernel for the target SAP system. The required minimum patch level of the kernel is 753 PL100.

Requirements depending on the source database:

 All other database types according to PAM.

 

V) Target Database SAP MaxDB

• Currently only available on request. If you are interested in SAP MaxDB as target database,
  contact SAP by reporting an incident on component BC-UPG-TLS-TLA that contains the following data:
  • details about the source and target levels regarding operating system, database, and ABAP
  • information about Unicode
  • a request to forward the incident directly to development support

Requirements depending on the source database:

 

All other database types according to PAM.

 

 

----------------< Update D029945 11/OCT/2021 >--------------------------
c) "DMO with System Move": Requirements and Restrictions

Requirements for Source System and Source Database:

• Source Database: All source databases excluding SAP HANA database
• Operating System (OS) of source primary application server (PAS) host: Any Unix-based or Windows operating system. In case of an IBM Db2 for i database, the PAS must always run on an IBM i Host.
• The operating system of the application server on the source host has to be supported for the source SAP release according to PAM. The operating system of the application server on the target host has to be supported for the target SAP release according to PAM.
• During a "DMO with System Move" run, dump files are created in the SUM folder that contain the contents of source database tables in compressed form. Since the entire source database is exported, make sure that there is enough space available.
• As of SUM 2.0 SP11, a particular phase checks for left-over data in physical table pools. This means that SAP Note 2930154 no longer needs to be applied before the start of the procedure.

Requirements for Target System and Target Database:

• Target Database: SAP HANA and SAP ASE only
• OS of PAS host: Any Unix-based or Windows operating system

Restrictions:

With regard to operating systems:

If the OS of the source and the target PAS hosts are different, you have the following options:

• On condition that
• the phase HOSTCHANGE_MOVE_SOT is finished on the source system
• you have copied the SUM directory from the source to the target application server (either manually, or using the script provided by the tool)

extract the SUM archive for the target OS over the target SUM directory to replace the executables.
Make sure that you use the same SUM version (including patch level) in the source and the target system. You have to consider this already when downloading the SUM archives!

• As a workaround, install in the source system an additional application server (AAS) that runs on the same OS as the target PAS host. In this way, source OS and target OS are identical.

With regard to scenarios and applications

• Migration of SAP SCM with automated LiveCache:
• Before you start the Software Update Manager, consider the consistency checks of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD (part A and B) to cleanup inconsistencies.
• Install the LCAPPS plug-in on the target database for the installation of the database instance in the target system. Make sure that you install the plug-in version that is compatible to SAP HANA database.
• Note that part A and B of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD run in the source system, but part C runs in the target system.
• Note also that due to technical restrictions, part A and B of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD run in roadmap step "Preprocessing", however only after the explicit decision to enter the downtime. Hence, they run in the SUM technical downtime. 

• Table comparison:

Checks are only supported if both the source OS on which the SUM is running, and the target platform have the same endianness. See SAP Note 552464 for more information on endianness.

• "DMO without System Update":
• You can combine “DMO with System Move” with the approach “DMO without System Update”. However, this is supported for target database SAP HANA only.
• Implement SAP Note 1903295 in the source system beforehand to prevent an abortion of phase JOB_RS_DMO_HDB_CONTENT_ACTIVATE with error message:
  "Batchjob 'RS_DMO_HDB_CONTENT_ACTIVATE' ... is aborted".

 With regard to SUM tool and systems

• SUM tool version:

Make sure that the release version and the patch level of the SUM tools are identical in both the source and the target system. To avoid different tool versions, we recommend to download the same SUM version for both systems, ideally at the same time.

• Change of the System-ID (SID):

Not possible.

• Short host names for source and target PAS:

They must be different. Otherwise the Software Update Manager does not start on the target system.
Note that fully qualified domain names are not affected.

• SAP HANA and SAP NetWeaver AS ABAP on one server (see also SAP Note 1953429):

The system ID of the database must not be the same as the system ID of the PAS on the source system.

• SUM on an AAS:

You may not run the SUM on an AAS if ASCS is not yet running separately (such as during the standard DMO procedure).

• Resetting the procedure on the target system:

As of SUM 2.0 SP12, you can now also select the reset function on the SUM user interface in the target system.
Note: If you use the reset function with the initial delivery of SUM 2.0 SP12 and then start a new SUM run, an error may occur in the INSTANCELIST_SERIAL phase with the following message:
SYSTEM MANAGER: System without sapcontrol is not allowed.
To solve the problem, restart the SAP start service manually. A solution is delivered with one of the following patch Level. This text is then adjusted accordingly.

• Resetting the procedure on the source system:

This works directly by using the reset option as described in the DMO guide.

• Support package (SP) version of SUM:

You need the identical SP and patch level version of SUM in both the source and target system. Pay particular attention to this when you download the SUM archive.

• AzCopy tool for file transfers when using the parallel mode:

Using the AzCopy tool (with option mirror-mode) is possible with AzCopy versions 10.15 and higher. For lower versions, the concept of SUM and AzCopy to check for complete file transmission are unsuitable.

-----------------< Update D029945 03/APR/2020 >--------------------------
--------------------< D029945 04/SEP/2019 >------------------------------
d) Downtime-Optimized DMO: Requirements and Restrictions

For further information regarding downtime-optimized DMO, see SAP Note 2547309.

 

-----------------< Update D031330 02/JUN/2021 >---------------------------
e) Downtime-Optimized Conversion to SAP S/4HANA: Requirements and Restrictions

For further information regarding downtime-optimized conversion to SAP S/4HANA, see SAP Note 3211805 or in the SAP Support Portal the page about Downtime-Optimized Conversion.

 

II/..... Corrections/Addenda to the Guide or Online Help:

.. / ..

III/.... Preparing the Update/Upgrade with DMO:

-------------------- < D044220 08/OCT/21 > ---------------------------
Avoid failure in phase MAIN_SWITCH/XCNV_LOAD due to table SATC_RT_RUN
During a SUM procedure with start release SAP_BASIS 710, 711, or 730 where DMO with System Move is applied, the table SATC_RT_RUN is converted.
However, if this table contains data, the conversion fails in phase MAIN_SWITCH/XCNV_LOAD. To prevent this, clear the entries in the table before starting the procedure.


--------------------< D023536 03/SEP/2020 >------------------------------
Set SAPGLOBALHOST parameter before you start DMO on Windows with target DB6
Before you start a SUM with DMO run

• on a Windows operating system
• with target database IBM Db2 for Linux, UNIX, and Windows (DB6)

make sure that the environment variable SAPGLOBALHOST is already set on the windows host on which the Software Update Manager is running.


---------------< Update D023536 30/OCT/2019 >--------------------------
--------------------< D023536 20/JUN/2016 >------------------------------
Target database SAP ASE for SAP BW systems: No changes after phase RUN_SMIGRCREATEDDL_740
Make sure that no further changes, such as activations, data loads to cubes, or field changes, are carried out in the SAP BW system after phase RUN_SMIGRCREATEDDL_740. Otherwise the migration might fail due to non-working partitioning.


----------------< Update D029945 12/JUN/2019 >---------------------------
--------------------< D029945 24/MAY/2019 >------------------------------
Benchmarking does not work on tables with more than 2 billion entries
If you want to run a migration benchmarking on a system with tables that have more than 2 billion entries, an error may occur similar to the following:

A1EEIMP 007 Task failed with error: (IMP) DbSlExeModify failed in insert for table '<tablename>' with 99
A1EEIMP 007 (IMP) SQL error = 2055
A1EEIMP 007 (IMP) maximum number of rows per table or partition reached

To avoid the error and to overcome this limitation, you may choose one of the following options:

• Partition Manually

You set a breakpoint for phase HDB_LANDSCAPE_REORG2 and manually partition the relevant tables with the following statements:

1. Logon to the source database with the technical SQL user of the SAP system
2. Determine the row count (<row_count_source>) with: SELECT COUNT(*) FROM "<table_name>"
3. Connect to the SAP HANA target database for the following statements using the SAP HANA Studio or SAP HANA Cockpit:
   1. Calculate the number of partitions with:
      select FLOOR(<row_count_source> /1000000000)+1 from dummy;
      (replace <row_count_source> with the actual number of rows in the source database)
      We recommended creating one partition per 1 billion rows, for example, 6 partitions for 5.2 billion rows.
   2. Determine the partition columns. Choose all primary key fields as partition fields. The primary key columns can be determined with:
      SELECT COLUMN_NAME FROM INDEX_COLUMNS WHERE TABLE_NAME = '<table name>' AND CONSTRAINT = 'PRIMARY KEY'
   3. Alter table with Hash Partition: ALTER TABLE "<table_name>" PARTITION BY HASH(<primary key column list>) PARTITIONS <num_partitions>
      Example for a table TAB1 has the primary key fields COL1, COL2 and COL3, and where 6 partitions should be created:
      ALTER TABLE "TAB1" PARTITION BY HASH("COL1", "COL2", "COL3") PARTITIONS 6

• Use report SMIGR_CREATE_DDL

The report SMIGR_CREATE_DDL exists on systems based on SAP_BASIS 731 or higher. Each of which must also have a sufficient support package level.
You may run the report to create the following required files:

• SQLFiles.LST (= text file containing a list of all SQL files generated)
• <package_name>.SQL  (= files containing SQL statements for the respective package)

Copy the files into the download directory before you start the benchmarking run.

• Use files from a previous benchmarking run

If you have already executed a benchmarking run on the same system, you can copy the relevant files SQLFiles.LST and <package_name>.SQL (see also option 2) into the download directory of SUM. Afterwards you can start the benchmarking again.

--------------------< D036661 21/NOV/2018 >------------------------------
Target database MaxDB only: Adjust parameter MaxDataVolumes
Before you start the Software Update Manager, you must adjust the MaxDB parameter MaxDataVolumes to avoid a MaxDB FULL error in phase EU_CLONE_MIG_DT_RUN. Make sure that

• the MaxDB database can increase its size with factor 3
• the MaxDataVolumes parameter has a three times higher value as the number of installed DataVolumes by SWPM
• the file system with the MaxDB volumes provides corresponding free space

Note that the parameter change requires a restart of the database.

--------------------< D065378 12/FEB/2018 >------------------------------
Target database SAP ASE: Preparing database only possible without SSL
Creating the DMO target database with enabled Secure Sockets Layer (SSL) using Software Provisioning Manager (SWPM) is not supported. For an existing SAP System, SSL can only be enabled by utilizing the system copy method of SWPM.


--------------------< D057031 30/JAN/2018 >------------------------------
SCM with liveCache to SAP HANA: Consider SAP Note 2562164
If you want to migrate an SCM liveCache to an integrated SAP HANA liveCache on an SAP HANA database within the SUM DMO procedure, you have to implement SAP Note 2562164 in addition to the SAP Notes requested during the SUM run in phase CHECK4NOTES_TOOL.


--------------------< D036390 21/JUN/2016 >------------------------------
Source database Db2 for i:  Review journal receiver backup strategy 
During Upgrade/Update processes SUM creates a great amount of additional data (ex. copy of the database), especially when using DMO.

Apart from the necessary disk space to keep table duplicates, this may create a significant amount of additional journal receiver data. To avoid unexpected disk shortages, review your journal receiver backup strategy during the upgrade process. Shorter save intervals to free up disk space may be advisable.


--------------------< D029945 03/MAY/2016 >------------------------------
Running DMO on AAS not supported for DB4 (IBM Db2 for i)
For DB4 (Db2 for i), the SUM has to be executed on the Primary Application Server (PAS) with operating system IBM i.


---------------< Update D029945 13/MAR/2017 >--------------------------
--------------------< D029945 29/FEB/2016 >------------------------------
Running DMO on AAS not supported if no ASCS instance exists
In general, SUM and SUM with DMO may be executed not only on the Primary Application Server (PAS), but also on an Additional Application Server (AAS). However, running SUM with DMO on an AAS is only supported if your system has a separate ASCS instance. It is not supported if the central services are part of the DVEBMGS instance.
In addition, running SUM with DMO on an AAS is only working if sapcontrol and sapstartsrv are existing and configured properly.


--------------------< D056915 09/FEB/2016 >------------------------------ 
Do not use report SAP_DROP_TMP_TABLES !
In some cases, it might be necessary to run report SAP_DROP_TMPTABLES to delete temporary BW objects, as described for example in SAP Note 1139396. However, if you perform a SUM run with DMO, you MUST NOT run the report SAP_DROP_TMP_TABLES due to its own logic of handling the temporary BW objects.


----------------< Update D023536 19/MAY/2020 >---------------------------
--------------------< D038245 01/SEP/2014 >------------------------------
Install digitally signed license
Make sure that you have a new digitally signed license installed before you start the DMO in your original system. This ensures that the license relevant for the migration key is properly recognized.


---------------< Update D050889 26/APR/2017 >--------------------------
--------------------< D050889 18/JUN/2014 >------------------------------
Migration of additional application server instances is not supported
The DMO of SUM does not support the migration of additional application server instances (also known as "dialog instances"). After the update of your SAP system and the migration on your target database, you have to reinstall the additional application server instances using the software provisioning manager 1.0 tool. Note: If the database SID is shown incorrectly during the installation, check section "6. Troubleshooting" of the DMO guide.


--------------------< D050889 14/APR/2014 >------------------------------
Environment variable SAPSYSTEMNAME needed for script "SUMSTART confighostagent"
Before you start the configuration of the SUM for the use with SAP Host Agent, as described in the DMO guide in section "3. Preparation" -> "Configuring SUM for Use with SAP Host Agent", make sure that the environment variable SAPSYSTEMNAME is set together with the SAP system ID (SAPSYSTEMNAME <SID>). Otherwise the script terminates with an error message.


--------------------< D037517 10/APR/2014 >------------------------------
Manual change or addition of HANA parameters
If necessary, it is possible to change or add HANA parameters during the DMO run in file ../SUM/abap/var/HDBCONFIG.LST. This file is created during the phase HDB_CONFDMP. After this phase, but BEFORE the phase HDB_CONFIG, you can maintain the file HDBCONFIG.LST according to your needs. Note, that you must revoke those values in this file which are not marked as "permanent" after the DMO run. Parameters tagged with “false” can be reset after the migration.


--------------------< D057031 17/FEB/2014 >------------------------------
(Windows only:) Enabling remote dialogue instance for HANA database after the downtime
If you use a remote dialogue instance, you must carry out the following post-downtime steps (or at the end of the downtime) to configure the remote dialogue instance so that it is able to communicate with the migrated database (HANA):

1. Install hdbclient locally on dialogue instance host and make sure, that the path is set correctly.
2. Set the environment variable DBMS_TYPE to "hdb". This must be done this way:
1. Use regedit to set the following entries:
   HKEY_LOCAL_MACHINE\SOFTWARE\SAP\$(SID)\Environment > DBMS_TYPE = hdb
   HKEY_CURRENT_USER\Environment  > DBMS_TYPE = hdb
2. Set DBMS_TYPE using the control panel as follows:
   Control Panel\System and Security\System -> Advanced System Settings -> Advanced -> Environment Variables
1. User variables for $(sid)adm: Change DBMS_TYPE to "hdb"
2. System variables: Change DBMS_TYPE to "hdb"

IV/.... Problems during the Update/Upgrade with DMO:

---------------------< D044220 APR/13/2022 >--------------------------
Error in phase MAIN_POSTPROC/SQLEXE_CHECK_LOADUNIT
During the SUM run with DMO, all tables are newly created, ideally with the properties according to the ABAP Dictionary. If the load unit is set to "Page Preferred", the setting at database level is optional. Nevertheless, SUM checks in this case whether the tables were created with the setting "Page Loadable" as they were newly created during the procedure.
If the creation statement of a table has been overwritten by an SQL file, for example, because the table is partitioned, a discrepancy between the ABAP Dictionary and the database is detected. As a result, an error occurs in phase MAIN_POSTPROC/SQLEXE_CHECK_LOADUNIT. You can ignore the error with the corresponding option on the SUM user interface.
Alternatively, you can change the table setting on the database using the following SQL command:

ALTER TABLE "<table_name>" PAGE LOADABLE

Example: The table EDID4 can be changed as follows: ALTER TABLE "EDID4" PAGE LOADABLE
The problem is solved in a later version of SUM.

-------------< D050889 05/OCT/2021 >--------------------------
DMO with System Move: Phase START_SHDI_PREPUT aborts due to incorrect RFC Login credentials
You are running your system with different DDIC passwords in source and target system. Therefore, the RFC Login to the shadow instance is not possible.
The log file START_SHDI_PREPUT_NEW.LOG displays the following error message: 2WETQ231 RFC Login failed
To solve the problem, change the DDIC password in the shadow instances to the value of the source system as described in SUM guide in: A.Appendix -> A.3 Administration -> Changing the DDIC Password.


---------------------< D050889 SEP/24/2020 >--------------------------
Error in phase STARTSAP_MIG_DT
The sapcontrol StartWait returns the error message "FAIL: Timeout"or "FAIL: Fork failed". The reason is that the SUM instance is restarted after the change to a single instance setup, and the change of the message server or enqueue server ports may lead to inconsistencies of the instance configuration. To solve the issue, repair the SAP Startservice by manually calling the sapcontrol command RestartService/Bootstrap. Otherwise, a manual restart of the SUM Instance is required.


-----------------------< D023536 OCT/29/2019 >--------------------------
Target database SAP HANA: CV_CPRO and CV_StructureElement activation error
During a database migration to SAP HANA, the activation of CV_CPRO and CV_StructureElement failed.
For more information and to solve the issue, see SAP Note 2844868.


--------------------< D050889 10/OCT/2018 >------------------------------
Target kernel detection failed in phase SCANDIR_MIGKERNELS
The DMO procedure expects the SAP Kernel archives with the same or a higher release version to be located in the download directory. If the source system is already equipped with the latest SAP Kernel archives, including the latest patch archives, the SAPEXE or SAPEXEDB archives found can be rejected. The DMO procedure does not take into account the patch archives here.
Solution: Wait for newer archives on the SAP Marketplace, or perform an SAP Kernel downgrade.


--------------------< D036390 15/MAR/2018 >------------------------------
Source database IBM Db2 for i: Lock problem in phase SCEXEC_REVTRIG_DEL during reset
If you have to reset your DMO procedure, a lock problem may occur in phase SCEXEC_REVTRIG_DEL with an error message of the following kind:

Severe error(s) occurred in phase REV_PREPROC/SCEXEC_REVTRIG_DEL!
Last error code set: 1
error(s) during parallel execution of processes, check 'SQLEXETD.LOG' for details
2 processes failed, check 'SCEXEC_R.*' for details
ERROR:
Detected the following errors:
# /usr/sap/B75/SUM/abap/log/PTTRDR06.LOG:
4 ETQ010 Date & Time: 20180221134913
3 ETQ398 SQL: DROP TRIGGER "TR_00006U"
4 ETQ399 Committing.
3 ETQ398 SQL: DROP TRIGGER "TR_00022I"
4 ETQ010 Date & Time: 20180221135147
1EETQ008 Error message: DBSL error 99 (db code -913):
1EETQ008 SQL0913 - Row or object /IWBEP/I_MGW_SRH in
1EETQ009XR3B75DATA type *FILE in use. (881838/SAPADM/SUMSTART)- Timeout: *UNKNOWN

To solve the issue, repeat the phase. If the error persists, please contact SAP, for example by reporting an incident with component BC-UPG-TLS-TLA.

--------------------< D023536 07/DEC/2017 >------------------------------
Non-HANA target database: Error in phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO
You are running a database migration to a target database other than SAP HANA database, and phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO ends with an error message such as:

2EETG001 Secondary index "/BI0/E0TCTHP24I-010" does not exist in the database
2EETG001 Secondary index "/BI0/E0TCT_C01-010" does not exist in the database

or similar messages for other tables. In this case, follow the instructions in SAP Note 2566863 and repeat the phase afterwards.

---------------< D023536 26/MAY/2017 >--------------------------
Phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO fails due wrong storage
Symptom: An error occurs in phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO, and the logfile RSDB02EN.<SID> contains the following error messages:

2EETG010 "/SAPAPO/ORDKEY" "is a rowstore table on HANA DB" "but column store in DDIC" " "
2EETG010 "/SAPAPO/ORDMAP" "is a rowstore table on HANA DB" "but column store in DDIC" " "
2EETG010 "/SAPAPO/STOCKANC" "is a rowstore table on HANA DB" "but column store in DDIC" " "
2EETG010 "MMRP_DATEVECS" "is a rowstore table on HANA DB" "but column store in DDIC" " "
2EETG010 "RPM_PERF_DATA" "is a rowstore table on HANA DB" "but column store in DDIC" " "
2EETG010 "RPM_PLAN_FILE" "is a rowstore table on HANA DB" "but column store in DDIC" " "

You can ignore these messages. Those tables shall stay in rowstore.


-----------------< D056915 13/FEB/2015 >------------------------------
TPL error in phase EU_CLONE_CRE_SHDVIEWS
You encounter an error in phase EU_CLONE_CRE_SHDVIEWS, which is described in log file SHDVIEWS_PRP<number>_IMP.LOG as follows:
(TPL) ERROR: unknown template variable "crestm"
To solve this error, replace the kernel tool R3ldctl (located in directory <SUM_DIR>/abap/exe ) with a new version with minimum patchlevel 29 or higher.  Afterwards repeat the phase EU_CLONE_CRE_SHDVIEWS.


--------------------< D026110 10/FEB/2014 >------------------------------
AIX only: TCP/IP connections hang
During data import processes with R3load on systems running AIX, it may occur that R3load processes get stuck and never finish. Other TCP/IP operations may be affected as well. See SAP Note 1976256 for more information.


--------------------< I043746 12/MAR/2014 >------------------------------
Batch job RS_UPG_TOOL_HMW aborted in phase RUN_SMIGR_CREATE_DDL
Symptom: The phase MAIN_SHDIMP/SUBMOD_MIG_UPTIME_PRP/RUN_SMIGR_CREATE_DDL stops with the error message, that the batch job RS_UPG_TOOL_HMW has aborted.
Solution: See SAP Note 902817 for more information and follow the correction instruction provided with this SAP Note.

-------------< Update D038245 20/AUG/2021 >--------------------------
-------------< Update D038245 12/JAN/2021 >--------------------------
-----------------< D023536 29/OCT/2015 >------------------------------
SAP systems 7.00 and lower: Migration key does not work
SYMPTOM: You are running a SUM with DMO run and your SAP source system bases on SAP BASIS release 700 or lower. You are asked to enter the migration key for installation number INITIAL and the key, which you requested on SAP Service Marketplace, does not work.
SOLUTION: Use the following migration key (valid until December 31, 2025): 1G5fdEM5049IrBzjt6TE5Pae


--------------------< D021956 17/MAR/2014 >------------------------------
Data corruption in tables with data type DECFLOAT during SAP HANA migration
Symptom: In rare cases, during a migration to SAP Hana, data corruption in DecimalFloat fields of tables might occur under certain circumstances. The affected fields receive a semantically wrong value, that is, such a field has a value in Hana that is different from the value in the source system (although being “technically” correct from a datatype perspective).
Solution: See SAP Note 1990894 for more information and follow the correction instruction provided with this SAP Note.


-----------------< D019500 15/SEP/2016 >------------------------------
Error in phase MAIN_NEWBAS/PARCONV_UPG regarding table T510L
During a system update to EHP8 FOR SAP ERP 6.0, an error in phase MAIN_NEWBAS/PARCONV_UPG with regard to table T510L may occur. The reason is that during the migration to SAP HANA database, pool tables are converted to transparent tables. If the pool tables contain inconsistent data, the conversion stops in phase PARCONV_UPG.
For more information and to solve the issue, see SAP Note 2349876.


--------------------< D028015 22/NOV/2013 >------------------------------
(BW:) Batchjob RS_UPG_TOOL_HMW failed in phase RUN_CUBE_CALC_VIEW_CREATE
Symptom: The phase MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE stops with the error message, that the batch job RS_UPG_TOOL_HMW has failed.
The reason is that the creation of an index for the master data terminates after the migration to the SAP HANA database. The error messages issued during the execution of the query are, for example:
"table config error; column store error: fail to create scenario/Index does not exist".
Solution: See SAP Note 1695112 for more information and follow the correction instruction provided with this SAP Note.


--------------------< D023396 13/NOV/2013 >------------------------------
(BW:) Batch job RS_UPG_TOOL_HMW aborted in phase RUN_CUBE_CALC_VIEW_CREATE
Symptom: The phase MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE stops with the error message, that the batch job RS_UPG_TOOL_HMW has aborted. Furthermore, you cannot enter the
characteristic value 0CALMONTH2 with SID 2 in table /BI0/SIOBJNM.
Solution: See SAP Note 1937899 for more information and follow the correction instruction provided with this SAP Note.


--------------------< D020263 22/NOV/2013 >------------------------------
(BW:) Batch job RS_UPG_TOOL_HMW aborted in phase RUN_CUBE_INDEX_ADJUST
Symptom: The phase MAIN_POSTP/RUN_CUBE_INDEX_ADJUST stops with the error message, that the batch job RS_UPG_TOOL_HMW has failed. Furthermore, the log-file DIR_SUM\abap\log\RSUPG_CUBE_INDEX_ADJUST.xxx displays the following error message:
A3WERSMIGR 155 Could not activate new index definition of table "/BI0/E0TCT_C01"
A3EERSMIGR 143 Error while modifying the index of table "/BI0/E0TCT_C01
Solution: See SAP Note 1940679 for more information and follow the correction instruction provided with this SAP Note.


-------------< D023536 09/Jan/2016 >--------------------------
Phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO fails due to missing views
Symptom: An error occurs in phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO, and the logfile RSDB02EN.<SID> contains error messages such as

• 2EETG002 View “M_AFRHB” does not exist in the database
• 2EETG002 View “M_AUKVC” does not exist in the database
• 2EETG002 View “M_FICOG” does not exist in the database
• 2EETG002 View “STERM_TXCO” does not exist in the database

Solution: Create all mentioned views using transaction SE14 (Utilities for Dictionary Tables) and repeat the phase afterwards.

V/..... Problems after the Update/Upgrade with DMO:


--------------------< D024828 10/SEP/2015 >------------------------------
SAP HANA/SAP ASE: Installation of additional application server instance fails
If the installation of an additional application server instance fails after an update or upgrade with DMO, see the following SAP Note for more information and to solve this issue:
After migration to SAP HANA: SAP Note 2136898
After migration to SAP ASE: SAP Note 2213003


--------------------< D029945 18/JUN/2014 >------------------------------
SCM with migration of empty SAP liveCache: Choose manual execution
If you want to migrate an empty SAP liveCache of your SAP SCM system (for example for testing purposes), you have to select the option "Prompt for manual execution" in the following SUM dialog about the liveCache:
"Before the downtime, the liveCache has to be saved and after the downtime it has to be restored. This is done using report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD section 'B' and 'C'. […] Do you want to run the report automatically or manually?".
An automatic execution will fail because there is no data in the liveCache download and the upload therefore won’t work. After you have selected the manual execution, two SUM dialogues will appear in the last part of the downtime to start the manual execution of these reports. When executing the reports you have the option to ignore the errors or to perform all steps in the sections but without download and upload of the liveCache data.

--------------------< D029945 06/JUN/2014 >------------------------------
SCM without SAP liveCache migration: liveCache connections LCA, LDA or LEA not working
After the DMO procedure on an SCM system with SAP liveCache, but where liveCache was not migrated, it can happen that the connections LCA, LDA, or LEA don't work correctly. Connection errors in automatic liveCache checks (such as transaction /sapapo/om03) can occur. To solve this issue, run the function module LC_RESTART_INFO (for example using transaction SE37). In some cases, a restart of SAP liveCache or the SCM system is necessary.


--------------------< D023536 12/MAR/2014 >------------------------------
DB02 shows unknown index in ABAP Dictionary
If you used the DMO with start release SAP_BASIS 710 to 730, transaction DB02 shows after the migration to SAP HANA the index CD0TBINDX1~F4 as unknown index in ABAP Dictionary.
You can drop this index in the database directly.

Part B: Chronological Summary

Date................Section...........Short description
-----------------------------------------------------------------------
29/JUL/2022...I...b3) DB6 as source database type: supported versions adapted
25/JUL/2022...IV....DMO with System Move: AzCopy supported with version 10.15 and higher
13/APR/2022...IV....Error in phase MAIN_POSTPROC/SQLEXE_CHECK_LOADUNIT
14/DEC/2021...I.....b3) Target Databases on request: text extended that explains how to create the request incident
11/OCT/2020...I.....c) Resetting the procedure on the target system
08/OCT/2021...III...Avoid failure in phase MAIN_SWITCH/XCNV_LOAD due to table SATC_RT_RUN
05/OCT/2021...IV....DMO with System Move: Phase START_SHDI_PREPUT aborts due to incorrect RFC Login credentials
02/JUN/2021...I.....b3) Target Databases (SAP ASE -> HANA)
26/JAN/2021...I.....c) DMO with system move: Identical SUM version in both the source and the target system
21/JAN/2021...IV....SAP systems 7.00 and lower: Migration key does not work
14/DEC/2020...I.....c) DMO with system move: Identical patch level of SUM in case of different OS on source and target system
23/NOV/2020 ..I.....c) DMO with system move: Move from Linux OS to Windows OS
07/OCT/2020...I.....c) DMO with system move: OS requirements text adapted
24/SEP/2020...IV....Error in phase STARTSAP_MIG_DT
03/SEP/2020...III...Set SAPGLOBALHOST parameter before you start DMO on Windows with target DB6
10/AUG/2020...I.....c) DMO with system move: Do not use AzCopy for file transfers
23/JUN/2020...III...SAP SCM system with automated LiveCache: restriction removed
28/MAY/2020...I.....b1) Operating Systems and Platforms
11/MAY/2020...I.....a) Release restrictions and limitations (stable application server)
09/APR/2020 ..I.....c) DMO with system move and different operatings systems
03/APR/2020...I.....d) Downtime-Optimized DMO
28/JAN/2020...III...SAP SCM system with automated LiveCache: Contact SAP beforehand to check for SAP Notes that may be necessary
27/JAN/2020...I....."DMO without System Update: Restriction for SAP SCM systems with activated LiveCache
22/JAN/2020...I.....Restrictions regarding databases, operating systems, and platforms (Source on Windows OS)
07/JAN/2020...I....."DMO with System Move": Requirements and Restrictions (Requirements for Source System)
18/DEC/2019...I.....Restrictions regarding databases, operating systems, and platforms (MS SQL source DB for Downtime-optimized DMO)
18/DEC/2019...I.....Restrictions regarding databases, operating systems, and platforms (SAP ASE: SAP_BASIS 730 requires at least SP04)
30/OCT/2019...III...Target database SAP ASE for SAP BW systems: No changes after phase RUN_SMIGRCREATEDDL_740 (changed phase name)
29/OCT/2019...IV....Target database SAP HANA: CV_CPRO and CV_StructureElement activation error
14/JUN/2019...I.....Restrictions regarding databases, operating systems, and platforms (MaxDB version updated)
12/JUN/2019...III...Benchmarking does not work on tables with more than 2 billion entries
01/FEB/2019...I.....Restrictions regarding databases, operating systems, and platforms (DB6 requires increased patch level)
24/JAN/2019...I.....Restrictions regarding databases, operating systems, and platforms (SAP ASE requires increased patch level)
21/NOV/2018...III...Target database MaxDB only: Adjust parameter MaxDataVolumes
08/OCT/2018...IV....Target kernel detection failed in phase SCANDIR_MIGKERNELS
25/JUN/2018...I.....Reason and prerequisite: SAP SCM SP-level requirements adapted 
28/MAY/2018...I.....a) Release restrictions and limitations (SAP NW 7.52 no target release for DMO)
16/MAR/2018...IV....Source database IBM Db2 for i: Lock problem in phase SCEXEC_REVTRIG_DEL during reset
12/FEB/2018...III...Target database SAP ASE: Preparing database only possible without SSL
30/JAN/2018...III...SCM with liveCache to SAP HANA: Consider SAP Note 2562164
07/DEC/2017...IV....Non-HANA target database: Error in phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO
26/MAY/2017...IV....Phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO fails due wrong storage
26/APR/2017...III...Migration of additional application server instances is not supported
13/MAR/2017...III...Running DMO on AAS not supported if no ASCS instance exists
07/MAR/2017...I.....Restrictions regarding databases, operating systems, and platforms (target 750 or higher requires Windows Server 2012)
09/JAN/2017...IV....Phase MAIN_POSTPROC/RUN_RSDB02CK_END_DMO fails due to missing views
19/SEP/2016...I.....Restrictions regarding databases (Target database DB6)
15/SEP/2016...IV....Error in phase MAIN_NEWBAS/PARCONV_UPG regarding table T510L
17/AUG/2016...Prerq..Prerequisites for SAP Business Suite systems (SCM with integrated liveCache)
21/JUN/2016...III...Source database Db2 for i:  Review journal receiver backup strategy
03/MAY/2016...III...Running DMO on AAS not supported for DB4 (Db2 for i)
26/FEB/2016...I.....Release restrictions and limitations: Unicode is prerequisite for 7.50 based target systems
09/FEB/2016...III...Do not use report SAP_DROP_TMP_TABLES !
02/OCT/2015...I.....Restrictions regarding databases, operating systems, and platforms
10/SEP/2015...V.....SAP HANA/SAP ASE: Installation of additional application server instance fails
15/MAY/2015...II....Table Migration Durations files end now with .XML
28/APR/2015...V.....Upgrade from SAP BW 7.4 SP08 to 7.4 SP12 or lower: Missing Database Index
27/FEB/2015...III...R3load requirements for Unicode Conversion
13/FEB/2015...IV....TPL error in phase EU_CLONE_CRE_SHDVIEWS
09/DEC/2014...I.....ATTENTION: DMO with Target Release 740 SP08 and Unicode Conversion
01/SEP/2014...III...Target release 7.4 and higher: Install digitally signed license
18/JUN/2014...V.....SCM with migration of empty SAP liveCache: Choose manual execution
05/JUN/2014...V.....SCM without liveCache migration: liveCache connections LCA, LDA or LEA not working
14/APR/2014...III...Environment variable SAPSYSTEMNAME needed for script "SUMSTART confighostagent"
10/APR/2014...III...Manual change or addition of HANA parameters
17/MAR/2014...IV....Data corruption in tables with data type DECFLOAT during SAP HANA migration
17/MAR/2014...I.....Restrictions regarding databases
12/MAR/2014...V.....DB02 shows unknown index in ABAP Dictionary
12/MAR/2014...IV....Batch job RS_UPG_TOOL_HMW aborted in phase RUN_SMIGR_CREATE_DDL
17/FEB/2014...III...Windows only: Enabling remote dialogue instance for HANA database after the downtime
10/FEB/2014...IV....AIX only: TCP/IP connections hang
22/NOV/2013...IV....(BW:) Batchjob RS_UPG_TOOL_HMW aborted in phase RUN_CUBE_INDEX_ADJUST
22/NOV/2013...IV....(BW:) Batch job RS_UPG_TOOL_HMW failed in phase RUN_CUBE_CALC_VIEW_CREATE
13/NOV/2013...IV....(BW:) Batch job RS_UPG_TOOL_HMW aborted in phase RUN_CUBE_CALC_VIEW_CREATE
06/NOV/2013...I.....Dual-Stack Split might be necessary

• DB6 version 9.7 FP5 or higher

• Note:
• DB6 versions 10.1 GA to 10.1 FP3 are not supported
• DB6 versions 10.5 GA to 10.5 FP7 are not supported
• DB6 version 11.1 MP1 FP1SAP is not supported on Windows